Sender device comtrolled data geographical location fencing method and system

ABSTRACT

A method and system are provided for remotely restricting data stored on the remote mobile communication device, sensor, or Internet of Things (IoT) device, by initiating a geographical restricting command when creating the data from a data originating mobile communication device, sensor or Internet of Things (IoT) device.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/998,024, filed Sep. 24, 2013, entitled MOBILE SENDER CONTROLLED DATAACCESS AND DATA DELETION METHOD AND SYSTEM by SPEEDE, Claremont, whichclaims benefit of U.S. Provisional Ser. No. 61/744,332, filed on Sep.24, 2012, and entitled MOBILE SENDER CONTROLLED DATA ACCESS AND DATADELETION METHOD AND SYSTEM, the specifications of which are incorporatedherein by reference in their entirety.

BACKGROUND—PRIOR ART

The following is a tabulation of some prior art that presently appearsrelevant:

U.S Patents Pat. No. Kind Code Issue Date App or Patentee 9,351,107 B2May 24, 2016 Ankit Nigam 8,423,791 B1 Apr. 16, 2013 Yan Yu 8,510,773 B1Aug. 13, 2013 Mitri Abou-Rizk 8,538,685 B2 Sep. 17, 2013 William J.Johnson 8,578,274 B2 Nov. 5, 2013 Adrian Druzgalski 8,700,003 B2 Apr.15, 2014 Elliot Klein 8,718,598 B2 May 6, 2014 William J. Johnson8,744,230 B2 Jun. 3, 2014 Gregory R. Hovagim 8,775,328 B1 Jul. 8, 2014Raj Abhyanker 8,850,473 B2 Sep. 30, 2014 Patrick Sheehan 8,971,930 B2Mar. 3, 2015 Andrew Andrey Li 8,983,978 B2 Mar. 17, 2015 EswarPriyadarshan 9,537,869 B2 Jan. 3, 2017 Erik L. Peterson

Existing geo-fenced location systems do not allow the sender of the datato have control over the geographical location of the receiver of thedata. Existing geo-fenced location solutions are controlled by a centrallocation, outside the control of the actual data creator. With existinggeo-fencing location systems, the restrictions placed on roamingcapabilities of the receiver device is left to a central system, acarrier and or the actual receiver device.

Accordingly, what is desired is a method for enabling the data sender,originating mobile communication device, a sensor or an Internet ofThings (IoT) device, to have the capability to set, at its ownconvenience, the geographical location fencing of their sent data,before the data is sent to the potentially geographical roaming receivermobile communication device, sensor or Internet of Things (IoT) device.Data, in binary or ASCII format, could be feature configurations for anIoT device, adding or restricting capabilities of a device based on thesensor's geographical location.

FIELD OF THE INVENTION

The present invention generally relates to methods and a data deliverystorage system, and more particularly, to methods and a data deliverystorage system for enabling the data sender, originating mobilecommunication device, a sensor or an Internet of Things (IoT) device, tohave the capability to set, at its own convenience, the geographicallocation fencing of their sent data, before the data is sent to thepotentially geographical roaming receiver mobile communication device,sensor or Internet of Things (IoT) device.

BACKGROUND OF INVENTION

Concerns about exposure of what was assumed to be confidential exchangesof information, has been the subject of debates aired over the media. Ithas become obvious that information, once transmitted, may be viewed bythird parties along the data communication pathway and by others, thedata receiver may choose to disclose it to. Many forms of data andcommunication encryption strategies address the communication pathwaydisclosure issue, but the end user receiver disclosure still exists. Inthe mobile space, this problem is magnified several times, due to theobvious transient nature of end users. For example, the sender of thedata has no control over, or knowledge of the geographical location ofthe receiver of the data, after it has been sent. With existinggeo-fencing location systems, the restrictions placed on roamingcapabilities of the receiver device is left to a central system, GPS,cellular or WiFi location technologies. This scenario adds to theproblem of information leakage, multi-regional compliance issues andreduced operational governance control, which remains an issue even ifthe line of transmission is secure.

Elaborate security schemes are available to ensure confidentiality,compliance and operational governance control are ensured. However, themobile recipient is not considered to be a member of the group of links,in the security chain, that may pose as a concern. For example, a sendertransmits an encrypted data to a mobile receiver, who successfullyreceives it; however as he is in transit, migrates to a geographicallocation that is outside of the sender's sanctioned zone for such datasensitivity level. The data migrating outside of an allowed geographicalzone, set by the data creator, may be a compliance or governanceconcern. As another example, a data sender, such as an originatingsensor or an Internet of Things (IoT) device, could have the capabilityto set, at its own convenience, the geographical location fencing of itssent data, before the data is sent to a potentially geographical roamingreceiver mobile communication device, sensor or Internet of Things (IoT)device. Data, in binary or ASCII format, could be feature configurationsfor the receiver device, adding or restricting capabilities of thedevice based on the sensor's geographical location.

Therefore, improvements for mobile device, sensor or Internet of Things(IoT) device communication and a method for managing sent data, by thedata sender device, or owner, are needed in the industry to address theaforementioned deficiencies.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention provide techniques that enable asender, using a mobile communication device, sensor or Internet ofThings (IoT) device to control the geographical location of the mobilecommunication device, sensor or Internet of Things (IoT) device at themoment of receiving the sent data, and after the data is stored.Essentially quarantining the sent data to a geographical locationdefined by the sending device, thus geo-fencing the source data. When areceiver attempts to roam to a geographical location outside of the datasender's defined limits, the receiver device will not be able to receivethe sent data. At this point, the sender may be notified that thereceiving device has migrated outside of the allowed sender definedgeographical location. If the data is already stored on the receiverdevice, and the device migrates outside the sender's allowedgeographical location, the stored data is deleted.

A further understanding of the nature and advantages of the inventionherein may be realized by reference of the remaining portions in thespecifications and the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form a partof the specification, illustrate embodiments of the present inventionand, together with the description, further serve to explain theprinciples of the invention and to enable a person skilled in therelevant art to make and use the invention.

FIG. 1 illustrates a mobile communication device, a sensor or anInternet of Things (IoT) device sender controlled data geographicallocation fencing network, in accordance with an embodiment of thepresent invention.

FIG. 2 illustrates communication channels in a mobile communicationdevice, a sensor or an Internet of Things (IoT) device sender controlleddata geographical location fencing network, in accordance with anembodiment of the present invention.

FIG. 3 is a flowchart depicting steps in the operation of a mobilecommunication device, a sensor or an Internet of Things (IoT) devicesender controlled data geographical location fencing delivery storagesystem, in accordance with an embodiment of the present invention.

FIG. 4A and FIG. 4B combined, is a flowchart depicting steps in theoperation of the process info process in a mobile communication device,a sensor or an Internet of Things (IoT) device sender controlled datageographical location fencing delivery storage system, in accordancewith an embodiment of the present invention.

FIG. 5 is a flowchart depicting steps in the operation theauthentication process residing in a mobile communication device, asensor or an Internet of Things (IoT) device sender controlled datageographical location fencing delivery storage system, in accordancewith an embodiment of the present invention.

FIG. 6A and FIG. 6B combined, is a flowchart depicting steps of a clientservice for a mobile communication device, a sensor or an Internet ofThings (IoT) device sender controlled data geographical location fencingdelivery storage system, in accordance with an embodiment of the presentinvention.

FIG. 7 is a flowchart depicting steps of the execution process of datain a client service for a mobile communication device, a sensor or anInternet of Things (IoT) device sender controlled data geographicallocation fencing delivery storage system, in accordance with anembodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION I. Introduction

The following detailed description of the present invention refers tothe accompanying drawings that illustrate exemplary embodimentsconsistent with this invention. Other embodiments are possible, andmodifications can be made to the embodiments within the spirit and scopeof the invention. Therefore, the detailed description is not meant tolimit the invention. Rather, the scope of the invention is defined bythe appended claims.

It would be apparent to one of skill in the art that the presentinvention, as described below, can be implemented in many differentembodiments of software, hardware, firmware, and/or the entitiesillustrated in the figures. Any actual software code with thespecialized control of hardware to implement the present invention isnot limiting of the present invention. Thus, the operational behavior ofthe present invention will be described with the understanding thatmodifications and variations of the embodiments are possible, given thelevel of detail presented herein.

FIG. 1 is a network 100 depicting a mobile communication device, asensor, or an Internet of Things (IoT) device sender controlled datageographical location fencing delivery storage network, in accordancewith an embodiment of the present invention. The network 100 includes auser device 102, a carrier wireless network 104, a Cellular M2M Networkor LoRa Gateway 108, and a data delivery storage system 106. As used inthis specification, user device 102 will commonly be a mobilecommunication device, a sensor, or an Internet of Things (IoT) devicehaving data communication capabilities, although one skilled in therelevant arts will readily appreciate that any communication device, ordevice having communication capabilities, can be substituted. Similarly,network 104 will commonly be a carrier wireless network throughout thisspecification, although one skilled in the relevant arts will likewiseappreciate that, depending on the capabilities of user device 102, othernetwork types, to include wired networks of any type, or wirelesstechnology of any type (e.g., Bluetooth, cellular, wi-fi, Low Power WideArea Network (LPWAN), such as LoRa LPWAN, Cellular M2M Network or LoRaLP Private Network, ad hoc, etc.), can be substituted for wirelessnetwork 104.

Data delivery storage system 106 eases the communications between senderand receiver user devices 102, by routing and storing data from senderuser device 102 to receiver user device 102, as further disclosed below,in accordance with an embodiment of the present invention. Furthermore,data delivery storage system 106 includes logic for establishingcommunications with user device 102 over carrier wireless network 104,and Cellular M2M Network or LoRa Gateway 108 in accordance with anembodiment of the present invention. Carrier wireless network 104 andCellular M2M Network or LoRa Gateway 108 is, in accordance with anadditional embodiment of the present invention, a cellularcommunications network.

II. Network Communications

FIG. 2 is a network 200 illustrating communication channels in a mobilecommunication device, a sensor or an Internet of Things (IoT) devicesender controlled data geographical location fencing network, inaccordance with an embodiment of the present invention. As previouslydisclosed, a user device 102 is operable to connect to a data deliverystorage system 106 over carrier wireless network 104 and Cellular M2MNetwork or LoRa Gateway 108 in order to send and receive data. Oneskilled in the relevant arts will recognize that a user device 102, suchas a mobile communication device, a sensor, or an Internet of Things(IoT) device, can communicate using a number of different protocols overa carrier wireless network 104 and Cellular M2M Network or LoRa Gateway108, such as a cellular communications network.

In accordance with an embodiment of the present invention, user device102 is configured to transmit data of any type over carrier wirelessnetwork 104. A carrier gateways 204 are used to receive the data 202communications from carrier wireless network 104 and forward thecommunications to data delivery storage system 106, in accordance withan embodiment of the present invention. In accordance with an additionalembodiment of the present invention, gateways 204 is a carrier GatewayGPRS Support Node (GGSN) and an SMS gateway Clickatell provided byClickatell (Pty) Ltd., of Redwood City, Calif. One skilled in therelevant arts will recognize that the precise configuration of thegateways 204 as shown in FIG. 2 need not exist in every system, whereinstead other means for forwarding the data 202 communications to datadelivery system 106 are implemented.

In accordance with an embodiment of the present invention, user device102 transmits data 202 to gateways 204 through the use of a special“short code” and Internet protocol address assigned to the data deliverystorage system 106, in order to allow gateways 204 to properly route thedata 202 to the data delivery system 106.

III. Operation of the Data Delivery Storage System

FIG. 3 is a flowchart 300 depicting an operational flow of data deliverystorage system 106, in accordance with an embodiment of the presentinvention. Flowchart 300 method begins at step 301 and proceeds to step302, where the data delivery storage system 106 receives data 202 fromthe user device 102. At step 304, the data delivery system 106 performsauthentication on the sender user or user device 102, then processproceeds to step 306. If authentication was unsuccessful 306, the methodproceeds to step 318 where processing ends. If authentication wassuccessful 306, the method continues to step 308.

At step 308 of flowchart 300, of the data delivery storage system 106,the data 202 is parsed. In the process of parsing the data 202, theintended destination user or user device 102 from some received data 202is extracted 310. Once extraction 310 is complete, step 312 of the datadelivery storage system 106 performs authentication on the destinationuser or user device 102, then process proceeds to step 314. Ifauthentication was unsuccessful 314, the method proceeds to step 318where processing ends. If authentication was successful 314, the methodcontinues to step 316.

At step 316 of flowchart 300, the message delivery storage system 106,the parsed data 202 is then repackaged into a data 202 format, andtransmitted to the intended destination user or user device 102, asfurther disclosed below, in accordance with an embodiment of the presentinvention. The method ends at step 318, in accordance with an embodimentof the present invention.

With continued reference to flowchart 300 of FIG. 3, the data deliverystorage system 106, and network 200 of FIG. 2, an example userinteraction with the data delivery storage system 106 is disclosed, inaccordance with an embodiment of the present invention. A user createsdata (binary, ASCII, or any file type), at user device 102 to bedelivered to a remote user device 102. In this example, the user createsdata. The user then sends this data to the remote user mobile device 102by entering a mobile number associated with the remote user mobiledevice 102. In accordance with an embodiment of the present invention,the data is sent to a short code, such as 45772, that uniquelyidentifies data delivery storage system 106.

At step 302 of flowchart 300, the data delivery system 106 receives thedata 202, and at steps 304 and 312 the data delivery system 106 performsany necessary authentication, as will be fully disclosed herein. Ifauthentications are unsuccessful 306 and 314, the process proceeds tostep 318. If authentications are successful 306 and 314, the processcontinues to step 308 and 316, respectively.

At step 308 of flowchart 300, the data delivery system 106 beginsparsing the data to identify a token, or tokens in the aforementioneddata, which represents the destination user or user device 102 from somereceived data 202, in accordance with an embodiment of the presentinvention. Next, this token is extracted 310 and step 312 of the datadelivery storage system 106, performs authentication on the destinationuser or user device 102. If authentication was unsuccessful 314, themethod proceeds to step 318 where processing ends. If authentication wassuccessful 314, the method continues to step 316.

At step 316 of flowchart 300, the data delivery system 106, the data isprocessed, which is described in more detail in FIG. 4, in accordancewith an embodiment of the present invention.

In accordance with an additional embodiment of the present invention, ifthe authentication of steps 306 and 314 fails, the process flow isterminated. In accordance with a further embodiment of the presentinvention.

IV. Process Information

FIG. 4A and FIG. 4B combined, is a flowchart 400 depicting a processinfo flow of the data delivery storage system 106, in accordance with anembodiment of the present invention. The method begins at step 401 andproceeds to step 402, where the data delivery storage system 106processes data 202 received from the user device 102. At step 402, thedata delivery storage system 106 determines if the data is abridged metadata. If data is abridged meta data, then process proceeds to step 404.If data is not abridged meta data, the method proceeds to step 414,which is described in more detail below. Meta data is a set of data thatdescribes and gives information about other data. Abridged meta data isinformation pertaining to what type of data will be sent, thegeographical location fencing data, configured by sender user device102, and an actual fingerprint or unique marker of the data that will besent. Non-abridged meta data is the resource or file system informationthat is linked to the abridged data that includes details such asstorage or location information. If a receiver device is outside of thesender created geo-fence, the linked meta data, abridged andnon-abridged, is automatically removed from the data delivery system 106during the deletion process. At step 404, the data delivery storagesystem 106 stores the meta data, and the geographical location fencing,geo-fence data, sent from the sender user device 102. Next, the datadelivery storage system 106 allocates network resources for data at step406. Allocated network resources is the entity which stores the data forexample, a hard drive, networked drive, external drive or a cloud systemthat stores the data. The network resources is a directory of the data.The data delivery storage system 106 then proceeds to step 408. At step408, the data delivery storage system 106 stores the allocated networkresource information. Next, the data delivery system 106 transmits theresource information at step 410 to the sender user device 102. Themethod then proceeds to step 412 where processing ends.

At step 414, the data delivery storage system 106 determines if the data202 is a data write success alert. If data is a data write successalert, then process proceeds to step 415. If data is not a data writesuccess alert, the method proceeds to step 420, which is described inmore detail below. At step 415, the data delivery storage system 106determines if the sender user device 102 successfully wrote data 202 tothe data delivery storage system 106 from the received alert. If thewrite was successful, then process proceeds to step 416. If the writewas unsuccessful, the method proceeds to step 417, which is described inmore detail below. At step 416, the data delivery storage system 106selects the stored non-abridged meta data created for the sender userdevice 102. Next, the data delivery storage system 106 transmitsnon-abridged meta data to the receiver user device 102 at step 418. Themethod then proceeds to step 412 where processing ends. At step 417, thedata delivery storage system 106 indicates the sender use device 102will attempt to rewrite data 202. The method then proceeds to step 412where processing ends.

At step 420, the data delivery storage system 106 determines if the data202 is an alert that the receiver user device 102 accessed sent data. Ifdata 202 was accessed, then the method proceeds to step 422. If data 202was not successfully accessed by the receiver user device 102, then themethod proceeds to step 424, which is illustrated and described in moredetail in FIG. 4B. At step 422, the data delivery storage system 106stores the result of the receiver user device's 102 access of thelocally stored data 202. The method then proceeds to step 412 whereprocessing ends.

The method continues in FIG. 4B at step 424 of flowchart 400 from step420, where the data delivery storage system 106 determines if the data202 was geo-fenced by the sender user device 102. If the data 202 wasgeo-fenced, then the method proceeds to step 428. If the data 202 wasnot geo-fenced by the sender user device 102, then the method proceedsto step 412 where processing ends.

At step 428, the data delivery storage system 106 determines the numberof receiver user devices 102 that successfully accessed data 202. If thenumber of receiver user devices 102 that accessed the data 202 isgreater than one, then the method proceeds to step 446. If only onereceiver user device 102 accessed the data 202, then the method proceedsto step 430.

At step 446, the data delivery storage system 106 determines if each ofthe receiver user device 102 is outside of the geo-fenced locationcreated by the sender user device 102. If the receiver user device 102is outside of the geo-fenced location, then the method proceeds to step432. If the receiver user device 102 is within of the geo-fencedlocation, then the method proceeds to step 448.

At step 432, the data delivery storage system 106 flag for deletion thedata 202 from the allocated resources whose receiver user device 102 isoutside the designated geographical location. The method then proceedsto step 434.

At step 434, the data delivery storage system 106 deletes the data 202from the allocated resources that was marked for deletion. Next, thedata delivery storage system 106 sends a receiver outside of geo-fencefor each receiver that is outside the designated geographical locationto the sender user device 102, at step 450. The method then proceeds tostep 412 where processing ends.

At step 448, the data delivery storage system 106 sends a retry dataaccess alert to each receiver device 102 that is inside the designatedgeographical location. The method then proceeds to step 412 whereprocessing ends.

At step 430, the data delivery storage system 106 determines if thereceiver user device 102 is outside of the geo-fenced location createdby the sender user device 102. If the receiver user device 102 isoutside of the geo-fenced location, then the method proceeds to step436. If the receiver user device 102 is within of the geo-fencedlocation, then the method proceeds to step 444.

At step 436, the data delivery storage system 106 flag for deletion thedata 202 from the allocated resources whose receiver user device 102 isoutside the designated geographical location. The method then proceedsto step 440.

At step 440, the data delivery storage system 106 deletes the data 202from the allocated resources that was marked for deletion. Next, thedata delivery storage system 106 sends a receiver outside of geo-fencefor the receiver that is outside the designated geographical location tothe sender user device 102, at step 442. The method then proceeds tostep 412 where processing ends.

At step 444, the data delivery storage system 106 sends a retry dataaccess alert to the receiver device 102 that is inside the designatedgeographical location. The method then proceeds to step 412 whereprocessing ends.

V. Operation of the Authentication Process

FIG. 5 is a flowchart 500 depicting an operational flow of theauthentication process of the data delivery storage system 106, inaccordance with an embodiment of the present invention. The methodbegins at step 501 and proceeds to step 502, where a search is performedin order to determine if the received unique properties can be found.The result is passed to step 504, in accordance with an embodiment ofthe present invention. At step 504, it is determined if the result is avalid user, by returning success and proceeding to step 506, if indeedthe result is a valid user. Step 504 proceeds to step 508, if the resultis determined not to be a valid user, in accordance with an embodimentof the present invention. The process then proceeds to step 510, whereit ends.

One skilled in the relevant arts will appreciate that additional meansfor authentication can be used, and the aforementioned means aredescribed by way of example and not limitation.

VI. User Device Client Service

FIG. 6A and FIG. 6B combined, is a flowchart 600 depicting anoperational flow of client service on the user device 102, in accordancewith an embodiment of the present invention, of transmitting andreceiving data (binary, ASCII, or any file type) 202, where by a senderuser device 102 can control the geographical location fencing of sentdata 202, on a remote receiver user device 102. The method begins inFIG. 6A at step 601 and proceeds to step 602, where the user device 102receives data 202 sent from a sender user device 102. At step 602, theremote receiver user device 102 performs a check to verify if data 202was received. If no data 202 was received, the method proceeds to step604. If data 202 was received, the proceeds to step 616, which isdescribed in more detail below, in accordance with an embodiment of thepresent invention.

At step 604 of flowchart 600, the client service, on the user device102, verifies if create new data option is selected, or create new datafrom a list of data templates on the user device 102, in accordance withan embodiment of the present invention. If it was not selected, step 604continues to step 602. If it was selected, the method proceeds to step606. At step 606, new data is created, or create new data from a list ofdata templates on the user device 102, in accordance with an embodimentof the present invention. Once the data is created, the method continuesto step 608.

At step 608 of flowchart 600, the client service, on the user device102, verifies if a geographical location fencing, geo-fence, is to beset on the data 202 when it is sent on the remote user device 102, inaccordance with an embodiment of the present invention. If nogeographical location fencing, geo-fence, is to be set, the methodcontinues to step 611, which packages the meta data, in accordance withan embodiment of the present invention. Once the meta data is created,the method continues to step 612. If geographical location fencing,geo-fence, is to be set on the data 202, the method continues to step610 where the data 102 is marked for geographical location fencing,geo-fencing. The method then continues to step 613 where the geo-fenceis created by selecting the geographical locations the data 102 isrestricted from being transmitted to.

At step 612 of flowchart 600, the client service, on the user device102, and transmits data 202 to the carrier wireless network 104, inaccordance with an embodiment of the present invention. The process thenproceeds to step 614, where it ends.

At step 616 of flowchart 600, the client service on the user device 102,signals that a data 202 is meta data sent from the sender user device102. The process then proceeds to step 648. If data 202 is not metadata, then the process proceeds to 624, which is illustrated anddescribed in more detail in FIG. 6B.

At step 648 of flowchart 600, the client service, on the user device102, the data 202 is accessed and locally stored on the receiver userdevice. One skilled in the relevant arts will recognize that step 648can be accomplished by various methods within user device 102, inaccordance with an embodiment of the present invention. The process thenproceeds to step 618.

At step 618 of flowchart 600, the client service, on the user device102, determines if the data 202 is geographical location restricted,geo-fenced. If the data 202 is geographical location restricted,geo-fenced, the process proceeds to step 640, which is described in moredetail below. If the data 202 is not geographical location restricted,geo-fenced, the process proceeds to step 630, which is illustrated anddescribed in more detail in FIG. 6B.

At step 640 of flowchart 600, the client service, on the user device102, determines if the receiver user device 102 is within the restrictedgeographical location, geo-fence. If the receiver user device 102 iswithin the restricted geographical location, geo-fence, the processproceeds to step 620, which is described in more detail below. If thereceiver user device 102 is not within the restricted geographicallocation, geo-fence, the process proceeds to step 630, which isillustrated and described in more detail in FIG. 6B.

At step 620 of flowchart 600, the client service, on the user device102, creates an outside geo-fence alert, then the process proceeds tostep 612, which is described in more detail above.

The method continues in FIG. 6B at step 630 of flowchart 600 from step618 and 640, the client service, on the user device 102, determines ifthe data 202 was successfully accessed and stored locally, as previouslyillustrated in FIG. 6A. One skilled in the relevant arts will recognizethat step 630 can be accomplished by various methods within user device102, in accordance with an embodiment of the present invention. If thedata 202 is successfully accessed and stored, the process proceeds tostep 632, which is described in more detail below. If the data 202 isnot successfully accessed and stored, the process proceeds to step 634.

At step 632 of flowchart 600, the client service, on the user device102, creates a successful read alert, then the process proceeds to step612, which is described in more detail above.

At step 634 of flowchart 600, the client service, on the user device102, creates an unsuccessful read alert, then the process proceeds tostep 612, which is described in more detail above.

At step 624 of flowchart 600, the client service, on the user device102, determines if the data 202 is amended meta data sent from the datadelivery storage system 106. If the data 202 is meta data sent from thedata delivery storage system 106, the process proceeds to step 626,which is described in more detail below. If the data 202 is not amendedmeta data sent from the data delivery system 106, the process proceedsto step 622.

At step 622 of flowchart 600, the client service, on the user device102, signals that the information has been received and gets stored.

At step 626 of flowchart 600, the client service, on the user device102, stores the amended meta data 202, then the process proceeds to step628.

At step 628 of flowchart 600, the client service, on user device 102,accesses allocated resources on the data delivery storage system 106 andstores data 202 (binary, ASCII, or any file type). One skilled in therelevant arts will recognize that step 628 can be accomplished byvarious methods within user device 102, in accordance with an embodimentof the present invention. The process proceeds to step 636.

At step 636 of flowchart 600, the client service, on the user device102, determines if the data 202 (binary, ASCII, or any file type) wassuccessfully accessed and stored locally. One skilled in the relevantarts will recognize that step 636 can be accomplished by various methodswithin user device 102, in accordance with an embodiment of the presentinvention. If the data 202 is successfully written, the process proceedsto step 654, which is described in more detail below. If the data 202 isnot successfully written, the process proceeds to step 638.

At step 638 of flowchart 600, the client service, on the user device102, creates a failed write alert, then the process proceeds to step612, which is described in more detail above.

At step 654 of flowchart 600, the client service, on the user device102, creates an successful write alert, then the process proceeds tostep 612, which is described in more detail above.

VII. User Device Data Usage

FIG. 7 is a flowchart 700 depicting an operational flow of data on theuser device 102, in accordance with an embodiment of the presentinvention, for the handling of received data 202 (binary, ASCII, or anyfile type). As previously illustrated in FIG. 6A and FIG. 6B,operational flow of the client service on the user device 102, step 622signals that a data 202 has been received and stores the received data202. One skilled in the relevant arts will recognize that step 622 canbe accomplished by various methods within user device 102, in accordancewith an embodiment of the present invention. The process then proceedsto step 702.

At step 702 of flowchart 700, determines if the receiver user device 102is within the restricted geographical location, geo-fence. If thereceiver user device 102 is within the restricted geographical location,geo-fence, the process proceeds to step 704, which is described in moredetail below. If the receiver user device 102 is not within therestricted geographical location, geo-fence, the process proceeds tostep 706, which is described in more detail below.

At step 704 of flowchart 700, demonstrates the user device 102 executingthe stored data 202. The process then proceeds to step 708, which isdescribed in more detail below.

At step 706 of flowchart 700, the mark and delete the received storeddata 202 for deletion on the user device 102. One skilled in therelevant arts will recognize that step 706 can be accomplished byvarious methods within user device 102, in accordance with an embodimentof the present invention. The process then proceeds to step 708.

At step 708 of flowchart 700 the user device 102 closes executed data202, then proceeds to the end at step 710, in accordance with anembodiment of the present invention.

IX. Advantages

From the description above, a number of advantages of some embodimentsof my sender controlled geographical location fencing method becomeevident:

(a) The sender of the data can maintain control over which geographicallocation the intended receiver may roam into, in order to and be grantedviewing, and or access privileges on the sent data.

(b) The receiver of the data no longer has equal control over theaccessed data, as the sender. The sender has superior, and sometimessole control over the sent data.

(c) The sender can send data other than text messages, such as binary,ASCII, or any file type.

(d) The sender has knowledge that the intended receiver has roamed intoa restricted geographical location.

(e) The sender device is the creator and owner of the data, as such, thesender dictates the which geographical location the data may existence.Not some other entity.

X. Conclusion

While various embodiments of the present invention have been describedabove, it should be understood that they have been presented by way ofexample only, and not limitation. It will be understood by those skilledin the relevant art(s) that various changes in form and details may bemade therein without departing from the spirit and scope of theinvention as defined in the appended claims. It should be understoodthat the invention is not limited to these examples. The invention isapplicable to any elements operating as described herein. Accordingly,the breadth and scope of the present invention should not be limited byany of the above-described exemplary embodiments, but should be definedonly in accordance with the following claims and their equivalents.

I claim:
 1. A method for deleting data initiated by a remote sender userdevice, the method comprising: A method of a data sender, havingquarantined the sent data to a geographical location defined by thesender, resulting in the one or more remote devices not be able toreceive the sent data, as they have entered a geographical location thatis outside of the data sender's defined geographical limits comprisingthe steps of: a. a sender device creating data; b. a sender sending thedata from the sender device, wherein the created data has an uniqueidentifier, wherein the unique identifier is a tag for subsequentlocation and the quarantining geographically location information ispreloaded in the user created data; c. the sender authenticating adestination user or user device, wherein a search is performed todetermine one or more properties associated with a valid user; d.receiving the created data on one or more remote devices, wherein thecreated data is stored on the one or more remote devices, with preloadedquarantining geographically location information; e. the one or moreremote devices verifying the receipt of the created data, wherein theunique identifier of the created data is verified by the sender device.2. The method of claim 1, wherein the step of the sender sending thedata further comprising the steps of: a. a data delivery storagefacilitating transmission of the data over the wireless network from thesender device to the one or more remote devices, wherein the datadelivery storage is in communication with the sender device and the oneor more remote devices; b. the data delivery storage parsing the createddata, wherein the one or more remote devices is identified by a tokenwithin the parsed data, wherein the quarantining geographically locationinformation within the parsed data is stored, wherein the created datais repackaged; c. the data delivery storage routing the created databetween the sender device and the one or more remote devices.
 3. Themethod according to claim 1, wherein the step of receiving the datafurther comprises of authenticating the sender device by comparing aunique properties of the sender device to registered values for theunique properties.
 4. The method according to claim 3, wherein thesender device is a mobile phone, a sensor, or an Internet of Things(IoT) device, and further wherein the unique properties comprise of aphone number, or media access control address (MAC), or any combinationof unique device attributes.
 5. The method according to claim 1, furthercomprising the step of: comparing the unique properties of the remoteuser device to registered values for the unique properties.
 6. Themethod according to claim 5, wherein the one or more remote devices is amobile phone, a sensor, or an Internet of Things (IoT) device, andfurther wherein the unique properties comprise at least a phone number,or a media access control address (MAC), or any of the unique deviceattributes.
 7. The method according to claim 1, further comprising thestep of receiving a data executed alert to the sender device.
 8. Themethod according to claim 1, wherein the step of quarantining the sentdata to a geographical location defined by the sender, further comprisesthe steps of: a. a data delivery storage determining a number of the oneor more remote devices that accessed the created data; b. a datadelivery storage determining which of the one or more remote devices isoutside the sender defined geographical location that attempt to accessthe created data, wherein the created data is not accessible, whereinunique identified stored data is deleted, and wherein an outsidegeo-fence alert is forwarded to the sender device; c. a receiver deviceattempts to execute a locally stored data, while physically locatedoutside the defined geographical location, results in uniquelyidentified stored data being deleted a from the receiver device.
 9. Themethod according to claim 1, further comprising the step of receiving aoutside geo-fence alert on the sender device.